00 - Introduction

Robotics I

Poznan University of Technology, Institute of Robotics and Machine Intelligence

Laboratory 0: Introduction

Teachers

Let us introduce ourselves:

Notes: We highly recommend prior email contact as most of the issues can be solved through email/online meeting or we can find a more suitable time for a meeting if needed.

Consultation hours: Thursdays 11:15-12:45, A8B 2.5 (the room will change after 03.2025)

Consultation hours: Fridays 13:30-15:00, A5, CM 319 (A5)

Consultation hours: Wednesdays 10:00-11:00, CM 318 (A5)

Consultation hours: Wednesdays 15:00-16:00, CM 318 (A5)

Class goals

  1. Show that robotics can be interesting and is usually a signficant part of AI/Computing courses abroad

  2. Teach students to not be scared when you see word robot in the job description as it may not involve hardware at all

  3. If it is not for you, we understand but just give it a try

  4. If you find it interesting then let us know

  5. Finally, we hope that you will know more after completing our course

AI in robotics and its applications

Sensory stack of an autonomous car is a great example as it start with proper sensory choices, mechanical and electric consideration, to AI algorithms processing the data, and finally the infrastructure to make it all happen. But robotics applications include many more areas like: * Agriculture * ADAS systems * Drones * Humanoids / Walking robots * Robots in warehouses * Space robots like Lunar rovers * Modern grasping techniques * … and many more.

Quick Q&A

A: Robot has usually a physical presence (hardware) and thus can sense/interact with the environment.

A: Seeing with your own eyes when it moves/operates intelligently based on your own algorithms.

A: It only works well when mechanical, electrical, and software components are operating well at the same time. If something is wrong, then nothing will work.

A: Of course, none knows everything and people specialize. There are mechanical engineers, electrical engineers, embedded engineers, AI engineers, infrastructure engineers (dev ops), etc. with all of them working together towards a final working robot.

Class roadmap

These are the topics we plan to cover during our labs:

  1. Introduction and showing what robotics is really about
  2. Linux/docker
  3. ROS 2
  4. ROS 2 part 2
  5. ROS 2 part 3
  6. Multi-sensory calibration (intrinsics and extrinsics)
  7. Object detection - training
  8. Object detection - deployment in ROS 2
  9. Object tracking
  10. Coordinate systems and transformations
  11. System control
  12. Kalman filter
  13. Turtlebot3 in simulation
  14. Turtlebot3 in simulation part 2
  15. Quiz, time to catch up

Class execution

This is a plan estimate and may change during the execution. Each class will use a single instruction available at PUT-JUG:

We will use eKursy to communicate and submit solutions. The key to join will be shared during the introduction class.

We are going to use Ubuntu and docker.

Class rules

  1. We treat students as adults and we expect the same treatment from you

  2. No eating or drinking in classes

  3. We will have 15 classes. One can have up to 2 unexcused absences. If you are sick/have a valid reason then send an email to your teacher.

  4. We will grade you based on homeworks and the final quiz. Homeworks are tasks from each instruction that should be completed with grading 0/1. Quiz will contain approximaty 30 A/B/C/D questions with each question having a single correct answer without any negative points for incorrect answers. The final grade will be based on quiz and you only pass if you submitted all homeworks.

Plan for today

Questions

Are there any questions?